Skip to content

chore(deps): update ethereum el/cl client updates - #825

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
renovate/ethereum-clients
Open

chore(deps): update ethereum el/cl client updates#825
github-actions[bot] wants to merge 1 commit into
mainfrom
renovate/ethereum-clients

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
ChainSafe/lodestar minor v1.45.0v1.47.0
Consensys/teku minor 26.7.126.8.0
NethermindEth/nethermind patch 1.39.21.39.3
erigontech/erigon minor v3.5.4v3.6.0
hyperledger/besu minor 26.7.126.8.1
paradigmxyz/reth minor v2.4.1v2.5.2
sigp/lighthouse patch v8.2.1v8.2.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

ChainSafe/lodestar (ChainSafe/lodestar)

v1.47.0

Compare Source

Good day Lodestar operators! We've just release v1.47.0 and recommend you upgrade your mainnet and testnet nodes. This one is BIG! We have moved our bls operations to Zig!! 🎉🎉 We are super proud to bring the first of many Zig releases to you as you will definitely notice performance benefits. But wait, there's more!!

We have been hunting for a bug in libp2p for a while, one that prevented graceful shutdown and this release has finally squashed that bug dead! You should not see any more issues with hanging shutdowns.

This is on top of all the work we've done to get ready for Glamsterdam. And ready we are. There is still some stuff you will see in the next release but for the most part your clients will be ready to rock and roll for the next fork. We just need to wait for scheduling to add the fork transition epochs into the codebase. Stay tuned...

We love you all and thank you for standing with us while we laid the foundation for a Zig encrusted future. We look forward to the next pieces that we will release and are excited to bring you more news in upcoming versions. Its going to be legen-wait-for-it-dary...

Full Changelog

Features
Bug Fixes
Performance
Refactoring
Dependencies
Continuous Integration
Tests
Styles
Maintenance
Documentation

v1.47.0-rc.0

Compare Source

Changelog

Full Changelog

Features
Bug Fixes
Performance
Refactoring
Dependencies
Continuous Integration
Tests
Styles
Maintenance
Documentation

v1.46.0

Compare Source

Good day Lodestar operators! We've just released v1.46.0, a recommended upgrade for all mainnet and testnet users. This release focuses on shutdown/restart stability, safer validator behavior while optimistic, and continued Gloas/Heze development for the upcoming forks and devnets.

If you build or run Lodestar from source with Bun, switch back to Node.js: Bun runtime support was removed. Node remains ^24.13.0. No migration is required for Docker or binary operators.

You may have noticed your nodes hanging on shutdown or restarts recently. We found, fixed a couple of bugs related to libp2p so you will now have smoother shutdowns and restarts. This will also fix a secondary effect that caused longer than normal re-sync times. Now the network-worker termination is bounded and no longer prevents finalized-state archiving before that process-manager kills the hanging shutdown. During our investigation we have found a latent bug in Node.js that we are tracking down and will get fixed. It is a pretty rare race condition that may affect shutdown in 1-ish percent of terminations. This will no longer affect state archival though as mentioned and your nodes will start up and sync quickly again.

We also fixed a weird edge case and in all circumstances, Lodestar will now refuses block production on optimistic heads, and the validator client skips sync-committee signing while the connected beacon node is optimistic.

The hanging process, that was mentioned above, highlighted an issue with far-behind-node head-state sync failure. It was only present if you were syncing from genesis though which is not a recommended process. This release fixed that bug and also provides better Gloas batch-failure classification, orphaned first-payload handling, and avoiding peer penalties for local EL failures.

Full Changelog

Features
Bug Fixes
Performance
Refactoring
Dependencies
Build System
Continuous Integration
Tests
Maintenance
Documentation

v1.46.0-rc.1

Compare Source

Changelog

Full Changelog

Features
Bug Fixes

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 6am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch 3 times, most recently from 3075fdd to a816f4c Compare August 20, 2026 13:19
@bussyjd
bussyjd enabled auto-merge August 22, 2026 22:35
@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch from a816f4c to 4436a8e Compare August 24, 2026 19:13
@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch 2 times, most recently from d8f04e7 to 24af408 Compare September 2, 2026 12:07
@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch from 24af408 to 44e6688 Compare September 2, 2026 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants